User-Centred Requirements Handbook |
The user requirements specification is complemented by the implementation plan. This defines how the user requirements that have been specified will be carried forward into the system design process. The plan can also be used to demonstrate to customers how user requirements have been dealt with after the system has been developed.
If product phasing is required, a statement of the migration path from the user's view is also produced. This will specify:
• The system configuration needed to match end user needs.
• The organisational changes necessary for users to gain maximum benefit.
• The planning stages to implement the system.
The section headings recommended for the user requirements plan and the type of information it should contain are shown in the table below (Form 3.12).
Form 3.12 - User Requirements Implementation Plan (Example)
| 3.12 User requirements implementation plan |
| System: New bank system |
|
1. Design rationale The system will be developed iteratively, starting with identification of the basic concepts for the interface. A number of simulations will be identified as a basis for the overall concept. The simulations that seem to have the most potential will be developed as interactive prototypes for user discussion and walkthrough. Finally the approach which receives the most user support will be taken forward and a full prototype will be created as a basis for the full system. Formal user trials will be carried out on the prototype to test if it meets the usability and acceptability goals set for it. |
|
2. Form of prototype Specify what form the system prototype will take: for example, paper, operational. |
|
3. Usability test method Specify the test(s) and test method(s) to be employed with the prototype(s) to examine usability, e.g. expert walk-through, diagnostics, user trials, etc. Where user trials are proposed, specify the subjects to be employed (e.g. number, ages, genders etc.). Add the results of usability testing. |
|
4. Acceptability test method Specify the test(s) and method(s) by which the product will be tested for acceptability e.g. user cost/benefits assessments, user trials, etc. Where field trials are proposed, specify the field site. Add the results of acceptability testing. |
|
5. Scope for iteration Specify the opportunities and constraints for re-testing usability and acceptability. |
|
6. User audit Specify how feedback on product usage, usability and acceptability will be collected. Add results of user audits. |
|
7. System phasing Specify how the system will be introduced. Describe the order in which different modules will be introduced. Also describe how users will be made aware of and introduced to the new system and in general terms what training will be provided. |